System, method and apparatus for system status identification in a wireless sensor network

ABSTRACT

A configured mode of operation of a wireless sensor network can be established through a dynamic remote configuration process. The plug-and-play universal sensor interface enables the monitoring capabilities of the wireless sensor network to scale seamlessly with the dynamic nature of changing sensor application objectives. A system status module enables a user to view the sensor service to confirm the current configuration of the wireless sensor network.

This application claims the benefit of and priority to provisionalapplication No. 61/992,307, filed May 13, 2014, and to provisionalapplication No. 62/136,959, filed Mar. 23, 2015. Each of the aboveidentified applications is incorporated herein by reference in itsentirety.

BACKGROUND

Field

The present disclosure relates generally to sensor applications,including a system, method and apparatus for system statusidentification in a wireless sensor network.

Introduction

Sensors can be used to monitor physical or environmental conditions.Wireless sensor networks can be used to collect data from distributedsensors and to route the collected sensor data to a central location.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features can be obtained, a more particular descriptionwill be rendered by reference to specific embodiments thereof which areillustrated in the appended drawings. Understanding that these drawingsdepict only typical embodiments and are not therefore to be consideredlimiting of its scope, the disclosure describes and explains withadditional specificity and detail through the use of the accompanyingdrawings in which:

FIG. 1 illustrates an example embodiment of a wireless sensor networkthat can collect and distribute sensor information.

FIG. 2 illustrates an example embodiment of a wireless node.

FIG. 3 illustrates an example embodiment of a sensor module unit.

FIG. 4 illustrates an example embodiment of a housing of a wireless nodethat exposes connector interfaces.

FIG. 5 illustrates an example embodiment of a housing of a sensor moduleunit.

FIG. 6 illustrates an example embodiment of a wireless node that isphysically attached to a plurality of sensor module units.

FIG. 7 illustrates an example embodiment of a configuration of a set ofsensor channels between a wireless node and a sensor module unit.

FIG. 8 illustrates a framework of the relative activation of sensors inthe wireless sensor network.

FIG. 9 illustrates a framework for enabling remote configuration of theoperation of a wireless sensor network.

FIG. 10 illustrates an example embodiment of remote configuration foractivation of sensor channels of data.

FIG. 11 illustrates an example embodiment of a system status feature.

FIG. 12 illustrates an example embodiment of detailed status informationprovided for a sensor channel of data.

DETAILED DESCRIPTION

Various embodiments are discussed in detail below. While specificimplementations are discussed, it should be understood that this is donefor illustration purposes only. A person skilled in the relevant artwill recognize that other components and configurations may be usedwithout parting from the spirit and scope of the present disclosure.

Sensors provide a mechanism for discovering and analyzing the state ofphysical or environmental conditions. Wireless sensor networks providean efficient mechanism for connecting with and retrieving sensor datafrom a distributed set of sensors. The growing emphasis on the Internetof Things (IoT) has further reinforced the importance of wirelessnetworks in connecting a range of devices. Notwithstanding today'semphasis on connecting a variety of devices using wirelesscommunication, it is recognized in the present disclosure that thepenetration of wireless sensor networks into the marketplace is limiteddue to the high level of installation and maintenance costs.

By their very nature, sensors are designed to measure a particularphysical or environmental condition. Sensors therefore represent a classof application-specific devices. Every sensor network installation canbe designed with unique cost constraints, measurement objectives, siterestrictions, or other application-specific requirements that caninfluence sensor network design. These application-specific qualitieslead to significant challenges in identifying a scalable solution thatcan be applied across various industries and markets. For example, it isrecognized that a scalable solution should be flexible in accommodatingnew types of sensor applications with little redesign or redeployment ofa wireless sensor network. Such a scalable solution would significantlyreduce installation and maintenance costs as new sensors and applicationfeatures are rolled out across an already deployed sensor networkinfrastructure. It is recognized that sensor network solutions shouldenable an evolution of the deployed wireless sensor network withoutwasting previously-deployed wireless sensor network elements orrequiring significant time or expense in modifying thepreviously-deployed wireless sensor network.

FIG. 1 illustrates an example embodiment of a wireless sensor networkthat can collect and distribute sensor information. The wireless sensornetwork can be configured to collect and distribute sensor informationthat is based on measurements by sensors deployed at monitored location110. Monitored location 110 can represent any area where a collection ofsensors is deployed. Monitored location 110 may or may not represent aphysical area having clearly defined boundaries. As would beappreciated, the extent of the monitoring application itself provides asense of boundary to monitored location 110. In one example, monitoredlocation 110 can represent a building such as a home, hotel, school,community building, stadium, convention center, warehouse, officebuilding, multi-dwelling unit, or other defined building structure. Inanother example, monitored location 110 can represent an area of controlsuch as a monitored area that can be fixed or movable.

Disposed within monitored location 110 is a plurality of sensors.Communication between the plurality of sensors and gateway device 120 isfacilitated by a set of wireless nodes 130-n. In general, wireless nodes130-n can be configured to form a wireless mesh network. In oneembodiment, the communication protocol between wireless nodes 130-n isbased on the IEEE 802.15.4 protocol. A wireless mesh network can beformed between wireless nodes 130-n and can be used to facilitatecommunication between any wireless node 130-n and gateway device 120.

A wireless node 130-n can be configured to support one or more sensormodule units (S), each of which can be individually coupled to awireless node 130-n via a plug-and-play universal sensor interface. Theplug-and-play universal sensor interface facilitates the separation ofthe wireless node communication infrastructure from the set of one ormore sensor module units that are deployed at the location at which thesupporting wireless node 130-n is installed. This separation createssignificant flexibility in choice of sensors that may or may not bedeployed proximate to the time of installation of the supportingwireless node 130-n. As such, the plug-and-play universal sensorinterface enables a sensor network solution to respond to changes in thesensor application requirements at monitored location 110 withoutincurring significant redeployment costs.

This flexibility would not be available if sensors were integrated witha wireless node. When a wireless node is deployed with integratedsensors, the monitoring capability of the wireless node is limited tothe sensors that were pre-installed in the wireless node. Thispre-installation would fix the capability of the wireless node at thetime of deployment and would limit the wireless node to a static sensorapplication objective. Thus, if a defective sensor needs to be replaced,or if another type of sensor needs to be added to meet a dynamic sensorapplication objective, then the wireless node would need to be replacedor otherwise modified. This would impact at least part of the wirelesssensor network infrastructure, which can result in sensor networkdowntime at the monitored location. A further impact would be producedas the maintenance expense of such a replacement or modification wouldbe prohibitive.

In the present disclosure, the plug-and-play universal sensor interfaceenables the sensor module units to be deployed separately from wirelessnodes 130-n. The plug-and-play universal sensor interface allows anytype of sensor module unit to be connected to any wireless node 130-n atany time and without any reconfiguration of the supporting wirelessnetwork infrastructure. This feature allows great flexibility in thedeployment and modification of wireless sensor networks at a lower pricepoint. Additionally, the plug-and-play universal sensor interfaceenables the monitoring capabilities of the wireless sensor network toscale seamlessly with the dynamic nature of changing sensor applicationobjectives.

In one example, a wireless node 130-n can be configured to support foursensor module units. As would be appreciated, the particular number ofsensor module units that can be supported by a wireless node 130-n canvary. Sensor module units can be added onto wireless nodes 130-nsequentially at different deployment times. Thus, for example, a firstsensor module unit can be added at a time of installation of thewireless node 130-n, with one or more additional sensor module unitsadded to the same wireless node 130-n in the future as needed to addresschanging sensor application objectives.

In one embodiment, each of the sensor module units can support aplurality of individual sensors. In one example, a sensor module unitcan support a set of eight sensors. In this example, the set of eightsensors can include sensors of one or more types. For example, sensorsin a sensor module unit can include one or more of the following: atemperature sensor, a humidity sensor, an air quality sensor (e.g., CO₂sensor), a light sensor, a sound sensor, a contact sensor, a pulsesensor, a water sensor, or any other type of sensor configured tomeasure a characteristic of a part of monitored location 110. A sensormodule unit can include multiple sensors of a single type. For example,a particular configuration of a sensor module unit can include fourpulse sensors, one temperature sensor, one humidity sensor, one airquality sensor, and one light sensor. In another example, a particularconfiguration of a sensor module unit can include eight sensors of asingle type. As would be appreciated, the set of sensors included withina particular sensor module unit can be chosen to meet a given sensorapplication objective.

In the present disclosure, it is recognized that sensor module units canbe targeted or otherwise designed for a particular class of sensorapplications. For example, one sensor module unit can be designed forsensor applications targeted to school buildings, while another sensormodule unit can be designed for sensor applications targeted to officebuildings. The sensor module unit targeted for school building use caninclude a set of sensors that are popular with school building sensorapplications. For instance, the set of sensors can include pulse sensorsfor measuring utility consumption (e.g., gas, water, electricity), atemperature sensor, an air quality sensor, a humidity sensor and a lightsensor. The sensor module unit targeted for school building use can thenbe selected for installation with wireless nodes deployed in schoolbuildings. In this manner, a relatively generic sensor module unit canbe deployed across many sensor application deployments in variousschools without requiring full customization for a specific applicationat a particular school. Production costs of the sensor module units arethereby minimized without any loss of flexibility in deployingcustomized sensor module units.

The impact on economies of scale can be readily appreciated. Wirelessnode modules can be produced on a larger manufacturing scale because thegeneric wireless nodes can be applied in many types of monitoredlocations in a manner that is separate from the particular sensorobjectives at the particular monitored location. Correspondingly, alimited number of types of sensor module units can be manufactured. Forexample, a first sensor module unit type can be produced for officebuilding applications and can include a suite of sensors typically usedin office buildings. Similarly, a second sensor module unit type can beproduced for school building applications and can include a suite ofsensors typically used in school buildings.

In the deployment at a particular monitored location, the genericwireless nodes can be installed at the particular monitoring points inthe monitored location with the particular type of sensor module unitattached to the generic wireless node to meet the particular needs atthat monitoring point. Customization of this nature is far superior tothe limited options presented by integrated devices. Customization neednot result in wireless sensor network downtime and can be effectedthrough the selective coupling of particular sensor module units towireless nodes.

A further benefit of this form of customization is that it obviates theneed to re-qualify and test wireless nodes to meet a new sensorapplication. Qualification need only be performed on new sensor moduleunits since the existing wireless network infrastructure provided by thegeneric wireless nodes had previously been qualified and tested. Thisreduces the time needed to bring new sensor network features to marketin addressing new market opportunities. If, on the other hand, sensorswere integrated with the wireless nodes, then the entire device wouldneed to be re-qualified and tested before being brought to market. Asdescribed, the plug-and-play universal sensor interface enables sensornetwork application customization without increasing installation andmaintenance costs of the sensor network infrastructure.

Returning to FIG. 1, wireless node 130-1 is illustrated as supporting asingle sensor module unit (S). Wireless node 130-2, on the other hand,is illustrated as not supporting any sensor module units. This exampleillustrates a scenario where wireless node 130-2 has been specificallyinstalled as a wireless relay node in a wireless mesh network tofacilitate a connection between wireless node 130-1 and gateway 120. Asfurther illustrated, wireless node 130-3 supports four different sensormodule units (S). This example illustrates a scenario where the sensingneeds of a particular part of monitored location 110 is greater andwould therefore require additional installed sensors at the location ofwireless node 130-3. For instance, wireless node 130-3 can be installedin a hub of sensing activity at monitored location 110, while wirelessnode 130-1 or wireless node 130-N can be installed in a periphery ofsensing activity at monitored location 110. The plug-and-play universalsensor interface enables sensor module unit deployment to match sensorapplication needs in a manner that scales seamlessly with the deployedwireless network infrastructure. Deployment and maintenance costs arethereby contained.

The wireless mesh network created by wireless nodes 130-n facilitatescommunication between sensor module units and gateway 120 via thewireless network infrastructure established by wireless nodes 130-n.Gateway 120 can be installed at monitored location 110 and can beprovided with network connectivity. For example, gateway 120 can beprovided with a network connection that facilitates communication ofsensor data to host system 140. The network connection can be embodiedin various forms depending upon the particular characteristics ofmonitored location 110.

For example, where monitored location 110 is a building in a developedarea, then the network connection can be facilitated by a wired Internetconnection via an Internet service provider. In another example, wheremonitored location 110 represents a remote physical area (or movablearea) that may or may not include a building structure, then the networkconnection can be facilitated by a terrestrial or satellite basedwireless network. As would be appreciated, the principles of the presentdisclosure would not be dependent on the particular form of networkconnection supported by gateway 120 in communicating with host system140.

The network connection between gateway 120 and host system 140 enablesthe collection of sensor data by host system 140. In one embodiment,host system 140 can be located in a location remote from gateway 120. Ingeneral, host system 140 can be configured to perform a collection ofsensor data from monitored location 110, storage of sensor data indatabase 142, and a distribution of sensor data to one or moredestinations. As illustrated, host system 140 can include one or moreservers 141 that can facilitate the collection, storage and distributionprocesses.

As described, wireless nodes 130-n provide a wireless networkinfrastructure upon which sensor module units can be deployed for acustomized sensor application. FIG. 2 illustrates an example embodimentof a wireless node. As illustrated, wireless node 200 includescontroller 210 and wireless transceiver 220. In one embodiment, wirelessnode 200 can be powered via a battery source (not shown). In anotherembodiment, wireless node 200 can be powered via an external powersource available at the point of installation at the monitored location.

Wireless transceiver 220 facilitates wireless communication betweenwireless node 200 and a gateway or another wireless node that operatesas a relay between wireless node 200 and the gateway. The sensor datacommunicated by wireless transceiver 220 is collected by controller 210via one or more universal sensor interfaces 230-n. Each universal sensorinterface 230-n can support connection of wireless node 200 with aseparate sensor module unit that can be attached to wireless node 200.

Universal sensor interfaces 230-n can represent a combination ofhardware and software. The hardware portion of universal sensorinterfaces 230-n can include a wired interface that enablescommunication of different signals between wireless node 200 and aconnected sensor module unit. In one example, the wired interface can beenabled through a connector interface, which is exposed by the housingof the wireless node 200, and that is configured to receive a sensormodule unit connector via removable, pluggable insertion.

In one embodiment, the wired interface can be based on a SerialPeripheral Interface (SPI) bus. In one example, the wired interfaceenables six connections: supply, ground, data in, data out, clock, anddevice select. The device select connection can be unique to each wiredinterface and can enable controller 210 in wireless node 200 to selectthe particular sensor module unit with which wireless node 200 desiresto communicate. The software portion of the universal sensor interfaces230-n can include a protocol that allows wireless node 200 tocommunicate with a sensor module unit.

In one example protocol, controller 210 can be configured to poll thevarious universal sensor interfaces 230-n to determine whether anysensor module units are connected. As part of this protocol, controller210 can first request a sensor ID from a sensor module unit. If theresponse read is 0, then controller 210 would know that no sensor moduleunit is connected to that universal sensor interface 230-n. If, on theother hand, the response read is not 0, then controller 210 would askfor the number of data values that have to be retrieved and the numberof bits on which the data values are coded. In one example, the higherorder 8-bits of a 16-bit communication between controller 210 and asensor module unit identifies the number of data values, while the lowerorder 8-bits of the 16-bit communication identifies the number of bitsused to code each data value. Based on the number of data values to beretrieved, controller 210 would then collect that number of data values,wherein each value can represent a different sensor channel of thesensor module unit.

In one example, a wireless node can be configured for coupling to fourdifferent sensor module units. If each of the sensor module units caninclude up to eight sensors, then the wireless node can be configured tocommunicate 32 sensor channels of data to the gateway via wirelesstransceiver 220.

In the illustration of FIG. 2, wireless node 200 also includes one ormore sensors 240-n. In one example, sensors 240-n can be containedwithin or otherwise supported by the housing of wireless node 200. Invarious scenarios, the one or more sensors 240-n can facilitatemonitoring at that part of the monitored location, including the healthand/or status of wireless node 200. In one example configuration,sensors 240-n can include a temperature sensor, a humidity sensor, avoltage sensor, a link quality sensor, or any other sensor that can beused to facilitate the sensing needs of wireless node 200.

As noted, wireless nodes can be designed as a generic communication nodeupon which customized sensing functionality can be added through theconnection of particular sensor module units. In this framework, thewireless nodes can be constructed with base communication functionalitythat can operate independently of particular sensors. As such, thewireless nodes can provide a relatively stable wireless networkinfrastructure that can support multiple generations of sensor moduleunits. As would be appreciated, the requirements of the sensor moduleunits would be dependent on the particular sensing application. Forexample, a first sensor module unit can be designed with a firstgeneration sensor having a first degree of accuracy, reliability, orother sensor characteristic, while a second sensor module unit can bedesigned with a second generation sensor of the same type having asecond degree of accuracy, reliability, or other sensor characteristic.As this example illustrates, different generations of sensor moduleunits can be attached to the same wireless node using the plug-and-playuniversal sensor interface. The original investment in the wireless nodewould not be lost should the second sensor module unit replace theoriginally-installed first sensor module unit. A low-cost evolutionarypath of the wireless sensor network would therefore be enabled thatcould scale seamlessly with a customer's needs, sensor technology, orother factor that implicates a sensor module unit modification.

FIG. 3 illustrates an example embodiment of a sensor module unitdesigned for attachment to a wireless node. As illustrated, sensormodule unit 300 includes controller 310 that communicates over auniversal sensor interface with the wireless node. In one embodiment,sensor module unit 300 supports a connector 320 configured forpluggable, removable insertion into a connector interface exposed by thewireless node. In another embodiment, the sensor module unit can becoupled to the connector interface exposed by the wireless node via aconnector attached to a cable.

Sensor module unit 300 can include a plurality of sensors 330-n. In oneexample, sensor module unit 300 includes up to eight sensors of one ormore types. In the present disclosure, it is recognized that a sensormodule unit can be pre-populated with a suite of sensors targeted to aparticular class of sensor applications. In this framework, a firstsuite of sensors can be used in a first sensor module unit targeted to afirst sensor application (e.g., school buildings), while a second suiteof sensors can be used in a second senor module unit targeted to asecond sensor application (e.g., office buildings) different from thefirst sensor application. Here, the underlying wireless networkinfrastructure can remain the same while particular sensor module unitsare chosen for coupling to one or more wireless nodes to facilitate aparticular sensor application at a monitored location.

The plug-and-play nature of the connection of sensor module units tosupporting wireless nodes facilitates a modular framework ofinstallation of a wireless sensor network. FIG. 4 illustrates an exampleembodiment of a housing of a wireless node that exposes a plurality ofconnector interfaces to produce the modular framework. As illustrated,wireless node 400 can have a housing configured to expose a plurality ofconnector interfaces 410. Each of the plurality of connector interfaces410 can support the physical attachment of a single sensor module unit.In the example illustration, each side of the housing of wireless node400 exposes a single connector interface 410. In the present disclosure,it is recognized that the housing of the wireless node can besubstantially larger than the housing of the sensor module unit. Thiscan result, for example, because the wireless node can be designed withadditional components such as an internal power source (e.g., battery)that can involve additional volume requirements as compared to thesensor module units. It is therefore recognized that one embodiment of awireless node can have multiple sensor module units physically attachedto a single side of the wireless node.

FIG. 5 illustrates an example embodiment of a housing of a sensor moduleunit that enables the modular framework. As illustrated, sensor moduleunit 500 supports a connector 510 that can be configured for pluggable,removable insertion into a corresponding connector interface 410 exposedby the housing of wireless node 400. The connection of sensor moduleunit 500 to wireless node 400 via the insertion of connector 510 intoconnector interface 410 produces a true plug-and-play framework ofwireless sensor network deployment.

FIG. 6 illustrates an example embodiment of a wireless node that isphysically attached to a plurality of sensor module units via universalsensor interfaces. As illustrated, wireless node 600 is attached tosensor module unit 620-1, sensor module unit 620-2, sensor module unit620-3, and sensor module unit 620-4 via four connector interfacesexposed by the housing of wireless node 600. The attachment of sensormodule unit 620-1 to wireless node 600 enables communication of sensordata between controller 621-1 and controller 610. The attachment ofsensor module unit 620-2 to wireless node 600 enables communication ofsensor data between controller 621-2 and controller 610. The attachmentof sensor module unit 620-3 to wireless node 600 enables communicationof sensor data between controller 621-3 and controller 610. Finally, theattachment of sensor module unit 620-4 to wireless node 600 enablescommunication of sensor data between controller 621-4 and controller610. Each of sensor module units 620-1 to 620-4 can be coupled towireless node 600 via a separate universal sensor interface having theconnectivity characteristics described above.

Controller 610 in wireless node 600 can communicate with each of sensormodule units 620-1 to 620-4 to retrieve sensor data generated by one ormore sensors on the respective sensor module units 620-1 to 620-4. Inone embodiment, the sensor channels of data that are communicated fromsensor module unit 620-n to wireless node 600 are configurable. Asnoted, communication between controller 610 and the sensor module units620-1 to 620-4 can be based on a protocol that enables identification ofthe number of data values that are transmitted from each of sensormodule units 620-1 to 620-4 to controller 610.

In one embodiment, a sensor module unit can be configured to transmitdata from only a subset of the sensors on the sensor module unit. Toillustrate this embodiment, consider again the example of a sensormodule unit targeted for school building use. In this example, thesensor module unit can include a standard suite of eight sensors,including four pulse sensors for measuring utility consumption (e.g.,gas, water, electricity), a temperature sensor, an air quality sensor, ahumidity sensor and a light sensor. Individual sensors in this standardsuite of sensors can be activated selectively such that only a subset ofthe sensor channels of data is forwarded from the sensor module unit tothe wireless node.

Here, it is recognized that the selective transmission of sensorchannels of data can be used to support efficient wireless bandwidth useor reduced power consumption within the wireless sensor network at themonitored location. Moreover, the selective transmission of sensorchannels of data can support a billing model where customers pay persensor channel stream of data that is exposed by the host system to thecustomer. Additionally, customization of a sensor module unit afterinstallation enables remote customization, which thereby lowers the costof installation and maintenance incurred by personnel responsible forconfiguring the wireless sensor network at the monitored location. Aswould be appreciated, this aspect of configuration can be designed toreduce the amount of pre-installation customization required in settingup sensor module unit 620-n to operate with wireless node 600 at themonitored location.

FIG. 7 illustrates an example embodiment of the configuration of a setof sensor channels between a sensor module unit and a wireless node. Asillustrated, wireless node 700 includes controller 710, while sensormodule unit 720 includes controller 721. Controller 710 in wireless node700 and controller 721 in sensor module unit 720 are configured tocommunicate using a universal sensor interface such as that describedabove.

In this example, assume that sensor module unit 720 includes eightsensors 722-1 to 722-8 (e.g., four pulse sensors for measuring utilityconsumption, one temperature sensor, one air quality sensor, onehumidity sensor and one light sensor), which can represent a standardsuite of sensors targeted for school building use. After sensor moduleunit 720 has been attached to wireless node 700 via a universal sensorinterface, channels of data associated with a first subset of the suiteof eight sensors 722-1 to 722-8 can be activated, while channels of dataassociated with a second subset of the suite of eight sensors 722-1 to722-8 can be deactivated.

For example, assume that sensors 722-1 to 722-4 are pulse sensors,sensor 722-5 is a temperature sensor, sensor 722-6 is an air qualitysensor, sensor 722-7 is a humidity sensor, and sensor 722-8 is a lightsensor. As illustrated, sensor module unit 720 can be configured suchthat channels of data associated with a first subset of sensors,including pulse sensor 722-1, temperature sensor 722-5 and humiditysensor 722-7 are activated. Correspondingly, sensor module unit 720 canbe configured such that channels of data associated with a second subsetof sensors, including pulse sensors 722-2 to 722-4, air quality sensor722-6 and light sensor 722-8 are deactivated. This example can representa scenario where the part of the monitored location at which wirelessnode 700 is installed has only one measurable utility consumption (e.g.,water) that requires monitoring along with a need for temperature andhumidity sensor readings.

Since channels of data associated with pulse sensors 722-2 to 722-4, airquality sensor 722-6 and light sensor 722-8 have been deactivated,controller 721 would report to controller 710 that controller 721 hasonly three data values for retrieval. These three data values arerepresented by the sensor channels 730-1, 730-4 and 730-7 that arepassed between controller 721 in sensor module unit 720 to controller710 in wireless node 700 over the universal sensor interface. As thisexample illustrates, the configuration of the activated/deactivatedsensor channels of data enables customization to meet the particularneeds of a particular part of a monitored location.

As noted, the wireless node can be coupled to a plurality of sensormodule units. Different subsets of sensor channels of data in eachsensor module unit can be activated/deactivated as needed. Incombination, a customized set of sensor channels of data across theplurality of sensor module units can be activated/deactivated as needed.

Here, it should be noted that the relative activation of sensor channelsof data in the wireless sensor network can be accomplished in a varietyof ways. FIG. 8 illustrates a framework of the relative activation ofsensor channels of data in the wireless sensor network. In thisillustration, wireless sensor node unit 800 can represent a combinationof a sensor module unit and a wireless node. In a manner similar to FIG.7, example wireless sensor node unit 800 is illustrated as containingeight sensors 822-1 to 822-8. In a configured mode of operation ofwireless sensor node unit 800, channels of data associated with a firstsubset of sensors is activated and channels of data associated with asecond subset of sensors is deactivated or managed in a manner differentfrom channels of data associated with the first subset of sensors. Thefirst subset of sensors, which includes sensor 822-1, sensor 822-5 andsensor 822-7, produces activated sensor data 821. Activated sensor data821 is transmitted to a gateway device via a wireless transceiver.

The selective transmission of activated sensor data 821 to a gatewaydevice is characteristic of the configured mode of operation of wirelesssensor node unit 800. The configured mode of operation can be effectedin a number of different ways.

In one embodiment, the configured mode of operation can be effected suchthat the second subset of sensors do not perform any sensormeasurements. In this embodiment, one or more components associated withthe second subset of sensors can enter an unpowered or other energysaving state such that power consumption is minimized. In general,maximizing power savings by powering down any unneeded component wouldmaximize the lifetime of internal powering solutions (e.g., batterypower). This extended lifetime would lower the maintenance costs of thewireless sensor network in delaying action by a service technician(e.g., replacing an internal battery).

In another embodiment, the configured mode of operation can be effectedsuch that a controller in the sensor module unit is prevented fromcollecting or otherwise retrieving data from the second subset ofsensors. In one example, the one or more of the second subset of sensorscan remain powered, but the controller in the sensor module unit doesnot collect or otherwise retrieve data from the second subset ofsensors. In one scenario, the interface between the controller and asensor in the second subset of sensors can be deactivated. FIG. 7provides an illustration of this scenario, where the interfaces betweencontroller 721 and sensor 722-2, sensor 722-3, sensor 722-4, sensor722-6 and sensor 722-8 are deactivated.

In another embodiment, the configured mode of operation can be effectedsuch that a controller in the sensor module unit has obtained sensordata from the second subset of sensors, but does not forward theobtained sensor data to the wireless node via the wired interface. Inone example, the second subset of sensors can continue to take sensormeasurements and forward those sensor measurements to the controller inthe sensor module unit. The controller can then be configured to forwardonly the sensor measurements from the first subset of activated sensorsto the wireless node.

In yet another embodiment, the configured mode of operation can beeffected such that the controller in the wireless node has obtainedsensor data from the second subset of sensors, but does not forward theobtained sensor data to the gateway via the wireless transceiver. In oneexample, the sensor module unit can continue to take sensor measurementsand forward those sensor measurements to the controller in the wirelessnode. The controller can then be configured to forward only the sensormeasurements from the first subset of activated sensors to the gateway.This embodiment is useful where wireless bandwidth in the wirelesssensor network is of concern. Effectively, the controller in thewireless node can be configured to filter the sensor channels that aretransmitted to the gateway.

As has been illustrated, the configured mode of operation of thewireless sensor node unit can limit the transmission of sensor data tothe gateway in a variety of ways. In various examples, the limitationeffected by the configured mode of operation can influence the operationof the sensors, the operation of the interface between the sensor andthe controller in the sensor module unit, the operation of thecontroller in the sensor module unit, the operation of the universalsensor interface, the operation of the controller in the wireless node,the operation of the wireless transceiver, or the operation of any othercomponent in the sensor data path. The particular mechanism used by theconfigured mode of operation would be implementation dependent. Ingeneral, the configured mode of operation can be designed to limit thecollection and/or forwarding of data in the data path originating at thesecond subset of sensors.

FIG. 9 illustrates a framework for enabling remote configuration of theoperation of the wireless sensor network at the monitored location. Asillustrated, host system 940 can support configuration station 950(e.g., personal computer, tablet, mobile phone, or other computingdevice). In one embodiment, host system 940 provides configurationstation 950 with computer readable program code that enablesconfiguration station 950 to render a user interface (e.g., webinterface). The user interface enables a user at configuration station950 to identify a configured mode of operation for the wireless sensornetwork. Through the interaction by a user with the user interfacepresented at configuration station 950, configuration station 950 cangenerate a configuration command that is transmitted to host system 940.In general, the generated configuration command can be designed toproduce one or more actions that influence or otherwise modify theoperation of the wireless sensor network.

In the illustrated example, the configuration command is received byhost system 940 and used as the basis for generating configuration setupinformation that is subsequently transmitted to one or more wirelessnodes such as wireless node 930-X. In the general sense, configurationsetup information can be used to influence or otherwise modify theoperation of any element in an upstream or downstream path between hostsystem 940 and a sensor module unit attached to a wireless node. Forexample, the generated configuration setup information can be used toinfluence or otherwise modify the operation of a component within hostsystem 940, gateway 920, wireless node 930-X, and/or a sensor moduleunit attached to wireless node 930-X.

By this process, configuration station 950 can be used to effect remoteconfiguration of the wireless sensor network. It is a feature of thepresent disclosure that the remote configuration provides furtherflexibility in enabling post-installment configuration. Features andcapabilities of the wireless sensor network would therefore not beconstrained to pre-installed features. Rather, features in the wirelesssensor network can be dynamically added or modified after theinstallation of a base of modular components. Installation andconfiguration costs of the wireless sensor network are thereforeminimized.

FIG. 10 illustrates an example embodiment of the use of remoteconfiguration for activation of sensor channels of data. As illustrated,configuration station 1050 supports the provision of a user interface1051 that enables a user to activate/deactivate particular sensorchannels of data at monitored location 1010. In one example, a settingsmodule supported by host system 1040 can transmit computer readableprogram code from a server device to configuration station 1050 thatenables configuration station 1050 to render user interface 1051.Through the interaction by the user with user interface 1051 onconfiguration station 1050, the user can specify the details ofparticular sensor channels of data that should be activated/deactivated.As noted, this activation/deactivation of sensor channels of data wouldeffect a change in the collection and/or reporting of sensor channels ofdata by a sensor module unit, a wireless node, a gateway, and/or a hostsystem.

User interface 1051 enables a user to specify a particular wirelessnode. In various embodiments, the wireless node can be specified using awireless node ID, a pseudo-name for the wireless node, or any othermechanism that enables individual identification of a wireless node. Thespecification of a particular wireless node can also be facilitated by agrouping of deployed wireless nodes per monitored location. In theillustrated example of FIG. 10, the identification of “Wireless Node X”would correspond to wireless node 1030-X at monitored location 1010.

After identification of wireless node 1030-X, user interface 1051 wouldthen enable the user to identify a particular port of wireless node1030-X. For example, where wireless node 1030-X includes four ports thatexpose interface connectors for physical attachment to a connector on asensor module unit, user interface 1051 would enable selection of one ofthe four ports. In the illustrated example of FIG. 10, theidentification of “Port Y” would correspond to the sensor module unitattached to port Y of wireless node 1030-X at monitored location 1010.

Next, user interface 1051 would enable the user to specify, for eachincluded sensor in the sensor module unit attached to port Y of wirelessnode 1030-X, whether that sensor channel of data is activated ordeactivated. In the illustrated example of FIG. 10, the user hasactivated the channel of data associated with Sensor 1, deactivated thechannel of data associated with Sensor 2, activated the channel of dataassociated with Sensor 3, . . . , and deactivated the channel of dataassociated with Sensor N.

Through the interaction by a user with user interface 1051, anactivation/deactivation status of each sensor channel of data in thesensor module unit attached to port Y of wireless node 1030-X would bespecified. The specification of the activation/deactivation status ofeach sensor channel of data can then be returned as a configurationcommand to host system 1040. In one embodiment, host system 1040 canstore an activation/deactivation status for each sensor channel of datain a database based on the received configuration command. In oneexample, the activation/deactivation status for a sensor channel of datais stored in accordance with an identifier based on a gatewayidentifier, a wireless node identifier, a port identifier and a sensoridentifier.

Based on the remotely-configured activation/deactivation status, hostsystem 1040 can then generate configuration setup information for theconfiguration of the sensor channels of data in the sensor module unitattached to port Y of wireless node 1030-X at monitored location 1010.In one embodiment, host system 1040 would transmit the generatedconfiguration setup information to wireless node 1030-X via gateway1020. The configuration setup information can then be used by wirelessnode 1030-X in configuring the operation of the sensor module unitattached to port Y and/or the operation of wireless node 1030-X. Afterconfiguration, wireless node 1030-X would transmit activated sensorchannels of data back to host system 1040 for subsequent distribution.

As noted above, the activation/deactivation of individual sensorchannels of data can effectively be performed at different parts of thesensor module unit and/or wireless node. The particular mechanism bywhich the configuration setup information would be used would thereforebe implementation dependent. For example, the configuration setupinformation can be used to influence the operation of the sensors, theoperation of the interface between the sensor and the controller in thesensor module unit, the operation of the controller in the sensor moduleunit, the operation of the universal sensor interface, the operation ofthe controller in the wireless node, the operation of the wirelesstransceiver, or the operation of any other component in the sensor datapath.

In one embodiment, the configuration setup information would not producea change in the transmissions by wireless node 1030-X, which can forwardsensor channels of data from all sensors. In this example, theconfiguration setup information can be used by gateway 1020 and/or hostsystem 1040 to influence the operation of gateway 1020 and/or hostsystem 1040 in forwarding only a select set of sensor channels of datathat have been activated. This selective transmission of sensor channelsof data can support a billing model where customers pay per sensorchannel stream of data that is exposed by the host system to thecustomer.

As has been described, user interface 1051 on configuration station 1050enables a user to remotely configure an activation/deactivation statusfor every sensor channel of data associated with every sensor in everysensor module unit attached to every wireless node at the monitoredlocation. Here, the activation/deactivation status specified atconfiguration station 1050 produces a change in the collection and/orprocessing of sensor channels of data that are performed by one or moreof a sensor module unit, a wireless node, a gateway, and a host system.This change in the collection and/or processing of sensor channels ofdata at units remote from configuration station 1050 enables a scalablewireless sensor network solution that reduces installation andmaintenance costs as the wireless sensor network evolves to addresschanging sensor application needs at a particular monitored location.

The activation/deactivation status specified at a configuration stationcan be performed as part of a dynamic reconfiguration process. There isno limit to the frequency of such changes in the activation/deactivationstatus. Rather, the frequency of such changes (e.g., daily, weekly,monthly, or any other frequency) is dictated by the changing sensorapplication objectives at the monitored location. These changes aredynamic. For example, where a customer is billed on a per sensor channelof data basis and on a per unit time basis (e.g., hourly, daily,monthly, or other specified time period), a customer can activate anddeactivate a sensor channel of data to only the times that it is neededto minimize the cost of such monitoring. In this example, the customercan configure the utilization of a sensor service as it relates to theactivation/deactivation of a particular sensor channel of data. In oneexample, the sensor service can represent an on-demand application thata customer can turn on/off based on customer needs. The granularityprovided by the dynamic reconfiguration process would therefore enable acustomer to have the usage of the sensor service scale in a manner thatfits within their unique utility vs. cost framework.

In the present disclosure, it is recognized that wireless sensor networkadministrators benefit from system status tools that enable them tospecify and confirm the current configuration of the wireless sensornetwork. The importance of this specification and confirmation of theoperational status of the wireless sensor network grows as theflexibility in the configuration and reconfiguration of the wirelesssensor network increases.

FIG. 11 illustrates an example embodiment of a system status feature ofthe present disclosure that facilitates such monitoring andconfirmation. In one embodiment, host system 1140 can include a settingsmodule that can transmit computer readable program code from a serverdevice to configuration station 1150 that enables configuration station1150 to render user interface 1151. In a manner similar to thatdescribed with reference to FIG. 10, user interface 1151 enables a userto activate/deactivate particular sensor channels of data at a monitoredlocation.

In response to the interaction by a user with user interface 1151,configuration station 1150 would transmit a configuration command tohost system 1140. Based on the received configuration command, hostsystem 1140 can generate configuration setup information for theconfiguration of the activation/deactivation of sensor channels of dataproduced at a monitored location.

In one embodiment, host system 1140 can include a system status modulethat can transmit computer readable program code from a server device tosystem status station 1160 (e.g., personal computer, tablet, mobilephone, or other computing device) that enables system status station1160 to render user interface 1161. In one embodiment, user interface1161 enables a user to view the status of various wireless sensornetwork components to confirm that the current configuration of thewireless sensor network matches the desired configuration. If thecurrent configuration of the wireless sensor network does not match thedesired configuration, then the sensor application objectives at themonitored location would be unable to be achieved.

In the example of FIG. 11, a status of the various sensor channels ofdata in the wireless sensor network at the monitored location isprovided via rows in a table rendered in user interface 1161. In theillustrated example, each row of the table can display columns ofinformation such as a Name, Port, Status, Range, Link Quality, SensorStatus, and Battery Level. Here, the Name column can refer to a wirelessnode identifier, the Port column can refer to the particular port of thewireless node to which a sensor module unit is attached, the Statuscolumn can refer to an operational status of the wireless node, theRange column can refer to a number of links between the wireless nodeand a gateway, the Link column can refer to a signal quality measurebetween the wireless node and the gateway or other wireless node, andthe Battery column can refer to a battery voltage level of the wirelessnode. Also included in user interface 1161 is section 1162, whichincludes separate Sensor Status columns for each of the sensor channelsof data supported by the sensors in a sensor module unit. In thisexample illustration, it is assumed that each sensor module unit affixedto a port of a wireless node can support up to eight sensors. Thus,section 1162 in user interface 1161 can include eight separate SensorStatus columns for each of the eight sensor channels of data produced bythe sensors in a sensor module unit. Section 1162 in user interface 1161can be used to reflect the evolution of the wireless sensor network atthe monitored location, wherein knowledge of the current status ofsensor channels of data is needed.

As noted above with respect to FIG. 10, a settings module in a hostsystem can be used to activate/deactivate individual sensor channels ofdata. As illustrated in user interface 1151, a user can specify theactivation/deactivation of the sensor channels of data supported by thesensors in the sensor module unit attached to Port Y1 of wireless nodeX1. As illustrated, the channel of data associated with Sensor 1 (AirQuality) is activated, the channel of data associated with Sensor 2(Light) is deactivated, the channel of data associated with Sensor 3(Temperature) is activated, . . . , and the channel of data associatedwith Sensor 8 (Humidity) is deactivated. Based on this userspecification, configuration setup information can be transmitted byhost system 1140 to the wireless sensor network at the monitoredlocation.

After activation/deactivation of the appropriate sensor channels ofdata, host system 1140 can receive and distribute sensor channels ofdata as needed. Host system 1140 can also receive status information(e.g., link range, link quality, battery level) that host system 1140can provide to system status station 1160 via a system status module. Aspart of this status information, host system 1140 can also confirm thatsensor channel information has been received and forwarded for activatedsensor channels of data, and whether sensor channel information has notbeen received or forwarded for deactivated sensor channels of data. Thestatus information is used by host system 1140 to generate theinformation displayed in user interface 1161.

As illustrated, section 1162 of user interface 1161 can provide statusinformation about the individual sensor channels of data supported bythe sensors in the various sensor module units at the monitoredlocation. As an example, the row for Node X1 would indicate in section1162 that the channel of data associated with Sensor 1 (Air Quality) isactivated, the channel of data associated with Sensor 2 (Light) isdeactivated, the channel of data associated with Sensor 3 (Temperature)is activated, . . . , and the channel of data associated with Sensor 8(Humidity) is deactivated. As this row displays, the relativeactivation/deactivation status for the channels of data associated withthe eight sensors contained in the sensor module unit attached to PortY1 of Wireless Node X1 is consistent with the configurationspecification shown in user interface 1151 of configuration station1150.

To further confirm that the wireless sensor network is configured asdesired, user interface section 1162 can also enable a user to gainfurther detailed information related to a particular sensor channels ofdata. For example, if a user selects the “T” user interface element inthe S3 column of Node X1, the user can then be provided with furtherdetailed information regarding that sensor channel of data.

FIG. 12 illustrates an example embodiment of detailed status informationthat can be provided for a sensor channel of data. As illustrated,system status station 1260 can render user interface 1261. Uponselection of the “T” user interface element in the S3 column of Node X1,user interface section 1262 can be produced that provides furtherdetailed information regarding that sensor channel of data.

In one example, the user can be provided with detailed monitored data(e.g., graph) of the history of the monitored temperature for thatparticular sensor channel of data. That historical data can be scaled toan appropriate time frame (e.g., hour, day, week, month, year, or othertime scale factor) to verify an operation status of that sensor channelof data. By this tool, a user can be made aware whether or not aparticular sensor channel of data that is supposedly activated isactually producing the desired data to meet a sensor applicationobjective. In another example, the user can be provided with detailedactivation data that can provide the user with a history of the relativeactivation and deactivation events. In one scenario, the start andduration of activation and deactivation periods for that sensor channelof data can be provided along with a cumulative measure of the relativeperiods of activation and deactivation. In another example, the user canbe provided with detailed cost data that can provide the user with ahistory of the cost incurred for the periods of activation of the sensorchannel of data. In one scenario, the costs of the sensor service forthat sensor channel of data can be broken down into an appropriate timeframe (e.g., hour, day, week, month, year, or other time scale factor)to verify the value proposition of the sensor service. As would beappreciated, user interface section 1262 can also include any other datathat can be used to confirm the operational status, history,effectiveness, or other utility measure as needed.

As has been described, the system status information provided enables anadministrator to confirm the configuration or reconfiguration of thewireless sensor network. Without such a system status tool, setup andmaintenance costs can increase as maintenance personnel would requireon-site inspection and analysis to confirm a desired configuration orreconfiguration of the wireless sensor network. These increased costswould limit the flexibility and application of the wireless sensornetwork. Additionally, the system status information supports theprovision of a sensor service, which enables customers to selectivelyactivate/deactivate sensor channels of data and evaluate theeffectiveness of the sensor service.

Another embodiment of the present disclosure can provide a machineand/or computer readable storage and/or medium, having stored thereon, amachine code and/or a computer program having at least one code sectionexecutable by a machine and/or a computer, thereby causing the machineand/or computer to perform the steps as described herein.

Those of skill in the relevant art would appreciate that the variousillustrative blocks, modules, elements, components, and methodsdescribed herein may be implemented as electronic hardware, computersoftware, or combinations of both. To illustrate this interchangeabilityof hardware and software, various illustrative blocks, modules,elements, components, methods, and algorithms have been described abovegenerally in terms of their functionality. Whether such functionality isimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system. Thoseof skill in the relevant art can implement the described functionalityin varying ways for each particular application. Various components andblocks may be arranged differently (e.g., arranged in a different order,or partitioned in a different way) all without departing from the scopeof the subject technology.

These and other aspects of the present disclosure will become apparentto those skilled in the relevant art by a review of the precedingdetailed disclosure. Although a number of salient features of thepresent disclosure have been described above, the principles in thepresent disclosure are capable of other embodiments and of beingpracticed and carried out in various ways that would be apparent to oneof skill in the relevant art after reading the present disclosure,therefore the above disclosure should not be considered to be exclusiveof these other embodiments. Also, it is to be understood that thephraseology and terminology employed herein are for the purposes ofdescription and should not be regarded as limiting.

What is claimed is:
 1. A method, comprising: receiving, at a host systemthat is remote from a monitored location, a configuration command forone or more of a plurality of sensor channels of data, the plurality ofsensor channels of data associated with a respective plurality ofsensors included together as a suite of sensors in a first of aplurality of sensor node units installed at the monitored location;transmitting, by the host system in response to the configurationcommand, configuration setup information to a gateway device at themonitored location for delivery to the first of the plurality of sensornode units, the configuration setup information enabling the first ofthe plurality of sensor node units to activate a first subset of theplurality of sensor channels of data; transmitting, by the host systemin response to a request that identifies the first of the plurality ofsensor node units, system status information that enables a display of aplurality of user interface elements corresponding to the plurality ofsensors supported by the first of the plurality of sensor node units,the plurality of user interface elements grouped together in the displayto represent the suite of sensors in the first of the plurality ofsensor node units, wherein a first subset of the plurality of userinterface elements corresponding to the first subset of the plurality ofsensor channels of data provide an indication of a first activationactivity, the first activation activity determined from a first userinstruction for the first subset of the plurality of sensor channels ofdata, and a second subset of the plurality of user interface elementscorresponding to a second subset of the plurality of sensor channels ofdata provide an indication of a second activation activity, the secondactivation activity determined from a second user instruction differentfrom the first user instruction for the second subset of the pluralityof sensor channels of data; and transmitting, by the host system,detailed sensor data upon receipt of a user initiated action associatedwith one of the first subset of the plurality of sensor channels ofdata.
 2. The method of claim 1, wherein the monitored location is abuilding.
 3. The method of claim 1, wherein the monitored location is aproperty area.
 4. The method of claim 1, wherein the first subset of theplurality of user interface elements include a description of a type ofsensor channel of data that has been activated.
 5. The method of claim1, wherein the indication of the first activation activity includesmonitored data during an activation state.
 6. The method of claim 1,wherein the indication of the first activation activity includesactivation state event data.
 7. The method of claim 1, wherein theindication of the first activation activity includes cost dataassociated with an activation state.
 8. A method, comprising: receiving,at a host system, activation information for a sensor channel of dataassociated with a sensor installed at a monitored location, theactivation information triggering an activation state for the sensorchannel of data applicable to a first time period; transmitting, by thehost system during the activation state, sensor information based on thesensor channel of data to a destination during the first time period;receiving, at the host system, deactivation information for the sensorchannel of data, the deactivation information triggering a deactivationstate for the sensor channel of data applicable to a second time perioddifferent from the first time period; restricting, by the host systemduring the deactivation state, a transmission of sensor informationbased on the sensor channel of data to the destination during the secondtime period; and transmitting, by the host system, status information toa client device, the status information including a measure of anactivity of the transmission of sensor information during the activationstate relative to an activity of the restriction of transmission ofsensor information during the deactivation state.
 9. The method of claim8, wherein the monitored location is a building.
 10. The method of claim8, wherein the monitored location is a property area.
 11. The method ofclaim 8, wherein the status information includes monitored data duringthe activation state.
 12. The method of claim 8, wherein the statusinformation includes activation state event data and deactivation stateevent data.
 13. The method of claim 8, wherein the status informationincludes cost data associated with the activation state.
 14. A system,comprising: a configuration server device configured to receiveactivation information for one or more of a plurality of sensor channelsof data associated with a respective plurality of sensors includedtogether as a suite of sensors in a first of a plurality of sensor nodeunits installed at a monitored location, the activation informationenabling the configuration server device to activate a first subset ofthe plurality of sensor channels of data; and a web server deviceconfigured to transmit, in response to a request that identifies thefirst of the plurality of sensor node units, system status informationthat enables a display of a plurality of user interface elementscorresponding to the plurality of sensors supported by the first of theplurality of sensor node units installed at the monitored location, theplurality of user interface elements grouped together in the display torepresent the suite of sensors in the first of the plurality of sensornode units, wherein a first subset of the plurality of user interfaceelements corresponding to the first subset of the plurality of sensorchannels of data provide an indication of a first activation activity,the first activation activity determined from a first user instructionfor the first subset of the plurality of sensor channels of data, and asecond subset of the plurality of user interface elements correspondingto a second subset of the plurality of sensor channels of data providean indication of a second activation activity, the second activationactivity determined from a second user instruction different from thefirst user instruction for the second subset of the plurality of sensorchannels of data, the web server device further configured to transmitdetailed sensor data upon receipt of a user initiated action associatedwith one of the first subset of the plurality of sensor channels ofdata.
 15. The system of claim 14, wherein the monitored location is abuilding.
 16. The system of claim 14, wherein the monitored location isa property area.
 17. The system of claim 14, wherein the first subset ofthe plurality of user interface elements include a description of a typeof sensor channel of data that has been activated.
 18. The system ofclaim 14, wherein the indication of the first activation activityincludes monitored data during an activation state.
 19. The system ofclaim 14, wherein the indication of the first activation activityincludes activation state event data.
 20. The system of claim 14,wherein the indication of the first activation activity includes costdata associated with an activation state.